-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve stability of package and tests #126
Conversation
I suppose it closes #93 too? For anyone merging it, I think we should add changelog entry too, since @jacekbogdanski improved ( |
Yes, of course, looks like I confused ticket numbers.
I wasn't sure about that because this change doesn't seem to matter from user perspective. But indeed in case if someone changes CDN URL into an empty string she/he will get console error instead of breaking the whole angular app. Changelog entry won't hurt. I've extracted ticket for updating failing tests / divarea leftovers: #127 |
Actually, I checked it right now and I see that a user gets exactly the same error message after proposed changes and the app behaves the same. I'm for skipping changelog entry and separate issue for that. |
Good point, I was thinking more about the improvement itself and that it can solve some real-live edge cases (since now we clear and reject promise correctly, which could cause some issues earlier), so it might be useful info for developers anyway (and additional changelog entry indicates that we are working actively on the integration which is good sign for developers too). WDYT? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job fixing the tests! They start to make sense when you look at them 🎉 Now let's polish this PR a little 😈 Besides the comments in code, please take a look below.
-
In
ckeditor.helpers.spec.ts
file we ignore one of the tests for IE10 - fortunately we officially don't support integration with this browser, so this check together with helpers can be removed. -
There is a double space
L386
that could be removed. -
PR lacks the change of
karma.conf.js
removing the unrandomising snippet:
jasmine: {
random: false
}
- After all I agree with @f1ames that it would be nice to have a changelog entry, mostly because we rarely have an opportunity to put there something different than updating CDN link or deps 🙈 I'll create an issue for 'Improving the stability of
getEditorNamespace()
function' and let's put it in changelog 🙂
Created #128 to provide a changelog entry here. |
There was something wrong with the commit history, so I re-rebased this branch onto latest master. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about that. Test still sometimes fails, probably also because of #127
I propose to do that once we fix #127 and we are sure that CI will be green with random order.
Well, the console.warn
tests are failing because you fixed them 😄 So CI will be red for now no matter if you run tests in order or randomly. So are we good with adding this Karma config? Or you meant something different?
Yeah, they are failing despite random order, so let's make it random by default. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems I was happy to early 😞 CI fails not only because of the console.warn
tests - on FF all tests fail 🦊 😿 (https://travis-ci.org/github/ckeditor/ckeditor4-angular/builds/715141554).
@jacekbogdanski please take a look what is going on there.
We come to the conclusion that it takes too much time to fix running tests in random order. Instead, we will just focus on improving overall asynchronous test correctness proposed in this PR. I've changed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job and pleasure working on this one, I see it took us 4 days but feels like really a lot was done here 👍
It's also kind of a strange feeling when we close 3 tickets but none of them is the one that was meant to be closed in the first place 😄
I've fixed some tests so the whole test suite is more stable now. Also, I've corrected the implementation of
getEditorNamespace
because:The tests are still failing because of
ckeditor4-angular/src/ckeditor/ckeditor.component.spec.ts
Lines 122 to 170 in dc423da
divarea
plugin for integrations. I will extract the issue as a separate ticket, as we should clean up the production code also.Proposed changelog entry
Closes #121
Closes #129.
Closes #128.